admin: Don't fail to deploy if there isn't a bootloader config
authorJavier Martinez Canillas <javier.martinez@collabora.co.uk>
Tue, 20 Aug 2013 14:28:34 +0000 (14:28 +0000)
committerColin Walters <walters@verbum.org>
Thu, 22 Aug 2013 09:52:16 +0000 (05:52 -0400)
commit6f6c87877eb1d9acafda3ad0b65c50ffab721d97
tree17478899f6cd3dd0a2db7dd606c0c461594e3f3d
parent8abad0b45218ca580dc5df2aaea687bc47e50210
admin: Don't fail to deploy if there isn't a bootloader config

Currently, when deploying an OSTree that does not contain a
bootloader configuration it fails with the following message:

"No known bootloader configuration detected"

A bootloader configuration is not strictly necessary if the
bootloader used is able to parse /boot/loader/entries on boot.

So, failing to deploy seems to be a little harsh. It is better
to just not write the bootloader configuration if a previous
one was not found but still swap the bootversion.

https://bugzilla.gnome.org/show_bug.cgi?id=706477

Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
src/ostree/ot-admin-deploy.c